Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1426

reference: 420-tree-1
name: 1426
tree-preservation-order: undefined
420-tpo-1
uprn
address-text
point: POINT (-1.006242 50.890900)
geometry: MULTIPOLYGON (((-1.006185 50.890894,-1.006187 50.890905,-1.006195 50.890915,-1.006208 50.890923,-1.006223 50.890928,-1.006241 50.890930,-1.006259 50.890929,-1.006274 50.890924,-1.006287 50.890916,-1.006296 50.890906,-1.006299 50.890895,-1.006296 50.890884,-1.006288 50.890874,-1.006276 50.890866,-1.006260 50.890860,-1.006242 50.890858,-1.006225 50.890860,-1.006209 50.890865,-1.006196 50.890873,-1.006188 50.890883,-1.006185 50.890894)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL